InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-02.Z/94-02/text0292.txt

Text File | 1994-02-28 | 3.6 KB | 88 lines

To quote Homer Simpson:
"Doooooooooooh!"

What I MEANT to say was the other socket libraries are based on UNIX
sockets, so you can't use window callbacks.  You can still do non-blocking
operations.

UNIX socket libraries I know about include:
1. IPC_SAP by Douglas Schmidt.  It seemed elegant to me, but I have not used
it, merely looked at it.  He has not posted it anywhere as far as I know (I
wrote him at [e-mail]).  If someone wants to volunteer (and it is
OK with Mr. Schmidt), I can email a copy to the administrator at a public
FTP site.

2. "SOCKET++  is a C++ iostream like library for sockets and pipes.  FTP
from uvaarpa.virginia.edu in /public_access/socket++/XX.tar.gz (where XX is
the version number)."

3. "A C++ socket library FTP from cs.ucl.ac.uk [128.16.5.31] in
coside/gnu/sockets++.tar.z."

(2) and (3) are from "The C++ Report", February 1994, column "The best of
comp.lang.c++".
======================================================================
Mark Fisher                            Thomson Consumer Electronics
[e-mail]           Indianapolis, IN

"Just as you should not underestimate the bandwidth of a station wagon
traveling 65 mph filled with 8mm tapes, you should not overestimate
the bandwidth of FTP by mail."
From [e-mail] Fri Feb 25 23:30:48 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA23658; Fri, 25 Feb 1994 19:27:40 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA15314; Fri, 25 Feb 1994 19:06:32 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Fri, 25 Feb 1994 23:30:48 GMT
From: [e-mail] (Charles (Chuck) Harrison)
Message-Id: <[e-mail]>
Organization: Netcom - Online Communication Services (408 241-9760 guest)
Sender: ses
References: <[e-mail]>, <[e-mail]>
Subject: Re: Term compiled to winsock?

In article <[e-mail]> [e-mail] (Tom Reynolds) writes:
>In article <[e-mail]> [e-mail] (John McDermott) writes:
>>Newsgroups: alt.winsock
>>From: [e-mail] (John McDermott)
>>Subject: Term compiled to winsock?
>
>>Does anyone have a version of TERM (ya know, that program which lets you
>>*pretend* you have a tcp/ip link instead of a plain one) compiled against
>>winsock? (ie has someone already done the porting?)
>>Thanks,
>>--john
>
>Term for winsock?  I don't see it as happening.  TERM relies heavily on
>certain UNIX-specific aspects of the OS if I remember correctly, and also does
>not use tcp-ip directly.  If you've run term, then you know that you don't use
>rsh or ftp, you use trsh, or termftp.  Therefore, you'd actually have to
>rewite the socket code in the winsock to use these "simulated" sockets.
>
>Sounds like a tough job to me.... Good luck though, I think it'd be an
>interesting project...

It _is_ an interesting project, and I say the first step is defining the
comm protocol accross the serial link which will support BSD-style sockets.
My suggestion is developing in the form of a proto-RFC at
  ftp://ftp.netcom.com/pub/cfh/sockets/ss002.txt

I now have access to both a Sun unix box w/4.1.3 (BSD-style) and a
vanilla 386 Windows box in one place, and I'm working on the learning curve
in my spare time...don't hold your breath :-).

Cheers,
 -Chuck   [e-mail]

>
>---
>Thanx!
>Tom Reynolds
>Department of Academic Computing, LaSalle University
>[e-mail]